Description Of Changes

Update Chakra theme and components to use new Ethyca brand colors and standardize the looks of some components like Badges.

Code Changes

• Update Chakra theme primary, secondary, complementary palettes
• Added new colors to Chakra theme
• Standardized the look of badges
• Updated admin homepage to use Cards

Steps to Confirm

Admin-UI

1. Browse around admin-ui pages
2. Check no purple or deep blue colors are present, they should be replaced with minos black
3. Check that the Fides logo is updated to it's uppercase version
4. Check that the homepage doesn't show an image, the links should now be gray cards with a left border of different colors

Privacy Center

1. Open privacy center homepage
2. Check icons are now Minos black instead of purple
3. Go to manage consent
4. Check the toggles are Minos black instead of purple

Fides-JS

1. Make sure you have a valid US Experience to test the fides-js modal:
2. Run the fides-js build, go to clients/fides-js and run npm run build
3. Go to http://localhost:3001/fides-js-demo.html?geolocation=us-ca&fides_locale=us
4. Click on Manage preferences
5. Check that the the modal now displays the button and the toggles in Minos black color instead of purple

Screenshots

Admin-UI

Privacy Center

Fides JS Banner, Modal, TCF

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
• Followup issues:
  • Followup issues created (include link)
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required